Programmatic Management of Software Resources in a Content Framework Environment

ABSTRACT

Methods, systems, and computer program products are disclosed for dynamically integrating software resources (such as web services and other back-end software resources) using the services of a content framework (such as a portal platform). A portlet model is leveraged to allow programmatic portlets to serve as proxies for web services, thereby extending portlets beyond their traditional visual role. A deployment interface and a system interface are described for these portlet proxies. The deployment interface is used for composing new web services, and a composition tool is described. The system interface allows for run-time management of the web services by the portal platform. The service provider for a particular function may be bound to the portlet proxy at development time or at run-time.

RELATED INVENTIONS

The present invention is a Divisional of U.S. patent application Ser.No. 11/759,799, filed on Jun. 7, 2007, which is a Continuation of U.S.patent application Ser. No. 11/247,360, filed on Oct. 11, 2005 (now U.S.Pat. No. 7,266,600), which is a Continuation of U.S. patent applicationSer. No. 09/956,268, filed on Sep. 19, 2001 (now U.S. Pat. No.7,035,944,issued Apr. 25, 2006), which is hereby incorporated herein by reference.The present invention is related to U.S. patent application Ser. No.09/956,276 (now U.S. Pat. No. 7,343,428), which is titled “Dynamic,Real-Time Integration of Software Resources through Services of aContent Framework”, and U.S. patent application Ser. No. 09/955,788 (nowU.S. Pat. No. 6,985,939), which is titled “Building Distributed SoftwareServices as Aggregations of Other Services”, both are which are commonlyassigned to International Business Machines Corporation.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to computer software, and deals moreparticularly with techniques for programmatic management of softwareresources in a content framework environment.

2. Description of the Related Art

The popularity of distributed computing networks and network computinghas increased tremendously in recent years, due in large part to growingbusiness and consumer use of the public Internet and the subset thereofknown as the “World Wide Web” (or simply “Web”). Other types ofdistributed computing networks, such as corporate intranets andextranets, are also increasingly popular. As solutions providers focuson delivering improved Web-based computing, many of the solutions whichare developed are adaptable to other distributed computing environments.Thus, references herein to the Internet and Web are for purposes ofillustration and not of limitation.

The early Internet served primarily as a distributed file system inwhich users could request delivery of already-generated staticdocuments. In recent years, the trend has been to add more and moredynamic and personalized aspects into the content that is served torequesters. One area where this trend is evident is in the increasingpopularity of content frameworks such as those commonly referred to as“portals” (or, equivalently, portal platforms, portal systems, or portalservers). A portal is a type of content framework which is designed toserve as a gateway, or focal point, for end users to access anaggregation or collection of information and applications from manydifferent sources. Portals are typically visual in nature, and providetheir users with a Web page known as a “portal page”. A portal page isoften structured as a single overview-style page (which may providelinks for the user to navigate to more detailed information).Alternatively, portal pages may be designed using a notebook paradigmwhereby multiple pages are available to the user upon selecting a tabfor that page. Some experts predict that portal pages will become thecomputing “desktop” view of the future.

Another area where advances are being made regarding dynamic content isin the so-called “web services” initiative. This initiative is alsocommonly referred to as the “service-oriented architecture” fordistributed computing. Web services are a rapidly emerging technologyfor distributed application integration in the Internet. In general, a“web service” is an interface that describes a collection ofnetwork-accessible operations. Web services fulfill a specific task or aset of tasks. They may work with one or more other web services in aninteroperable manner to carry out their part of a complex workflow or abusiness transaction. For example, completing a complex purchase ordertransaction may require automated interaction between an order placementservice (i.e. order placement software) at the ordering business and anorder fulfillment service at one or more of its business partners.

Many industry experts consider the service-oriented web servicesinitiative to be the next evolutionary phase of the Internet. With webservices, distributed network access to software will become widelyavailable for program-to-program operation, without requiringintervention from humans.

Web services are generally structured using a model in which anenterprise providing network-accessible services publishes the servicesto a network-accessible registry, and other enterprises needing servicesare able to query the registry to learn of the services' availability.The participants in this computing model are commonly referred to as (1)service providers, (2) service requesters, and (3) service brokers.These participants, and the fundamental operations involved withexchanging messages between them, are illustrated in FIG. 1. The serviceproviders 100 are the entities having services available, and theregistry to which these services are published 110 is maintained by aservice broker 120. The service requesters 150 are the entities needingservices and querying 140 the service broker's registry. When a desiredservice is found using the registry, the service requester binds 130 tothe located service provider in order to use the service. Theseoperations are designed to occur programmatically, without humanintervention, such that a service requester can search for a particularservice and make use of that service dynamically, at run-time. The webservices model is theoretically available for any type of computingapplication. However, the web services which are accessible fromregistries today are limited to relatively simple programs such as“Hello, World!” demo programs, programs which look up the currenttemperature for a particular zip code, programs which perform currencyexchange calculations, and so forth.

The core set of standards on which web services work is being builtincludes HTTP (“Hypertext Transfer Protocol”), SOAP (“Simple ObjectAccess Protocol”) and/or XML (“Extensible Markup Language”) Protocol,WSDL (“Web Services Description Language”), and UDDI (“UniversalDescription, Discovery, and Integration”). HTTP is commonly used toexchange messages over TCP/IP (“Transmission Control Protocol/InternetProtocol”) networks such as the Internet. SOAP is an XML-based protocolused to send messages for invoking methods in a distributed environment.XML Protocol is an evolving specification of the World Wide WebConsortium (“W3C”) for an application-layer transfer protocol that willenable application-to-application messaging, and may converge with SOAP.WSDL is an XML format for describing distributed network services. UDDIis an XML-based registry technique with which businesses may list theirservices and with which service requesters may find businesses providingparticular services. (For more information on SOAP, refer to “SimpleObject Access Protocol (SOAP) 1.1, W3C Note 8 May 2000”, which isavailable on the Internet athttp://www.w3.org/TR/2000/NOTE-SOAP-20000508. Seehttp://www.w3.org/2000/xp for more information on XML Protocol and thecreation of an XML Protocol standard. The WSDL specification is titled“Web Services Description Language (WSDL) 1.1, W3C Note 15 Mar. 2001”,and may be found on the Internet athttp://www.w3.org/TR/2001/NOTE-wsd1-20010315. For more information onUDDI, refer to the UDDI specification which is entitled “UDDI Version2.0 API Specification, UDDI Open Draft Specification 8 Jun. 2001”, andwhich can be found on the Internet athttp://www.uddi.org/specification.html. HTTP is described in Request ForComments (“RFC”) 2616 from the Internet Engineering Task Force, titled“Hypertext Transfer Protocol—HTTP/1.1” (June 1999).)

Application integration using these open standards requires severalsteps. The interface to a web service must be described, including themethod name(s) with which the service is invoked, the input and outputparameters and their data types, and so forth. WSDL documents providethis information, and are transmitted using a UDDI publish operation toa registry implemented according to the UDDI specification. Once theservice is registered in the UDDI registry, service requesters can issueUDDI find requests to locate distributed services. A service requesterlocating a service in this manner then issues a UDDI bind request, whichdynamically binds the requester to the located service using the serviceinformation from the WSDL document. (These UDDI operations have beenillustrated, at a high level, in FIG. 1.) SOAP/XML Protocol and HTTPmessages are commonly used for transmitting the WSDL documents and theUDDI requests. (Hereinafter, references to SOAP should be construed asreferring equivalently to semantically similar aspects of XML Protocol.Furthermore, it should be noted that references herein to “HTTP” areintended in a generic sense to refer to HTTP-like functions. Some UDDIoperations, for example, require HTTPS instead of HTTP, where HTTPS is asecurity-enhanced version of HTTP. These differences are not pertinentto the present invention, however, and thus no distinction is madehereinafter when discussing HTTP.)

The goal of web services is to provide service requesters withtransparent access to program components which may reside in one or moreremote locations, even though those components might run on differentoperating systems and be written in different programming languages thanthose of the requester. While a significant amount of work has been doneto define the goals, architecture, and standards on which web serviceswill be based, much work remains to be done to make web services operateeffectively and efficiently.

SUMMARY OF THE INVENTION

An object of the present invention is to provide a technique fordynamically integrating software resources (including, but not limitedto, web services) in a distributed network.

Another object of the present invention is to provide a technique forleveraging a portal model and framework for real-time integration ofsoftware resources as web services.

A further object of the present invention is to define techniques formaking software resources available for web services using a portletmodel.

Yet another object of the present invention is to define techniques forusing portlets as web service intermediaries.

Another object of the present invention is to provide a technique forenabling programmatic management of software resources used in webservices.

A further object of the present invention is to provide a compositionmodel for building web services as aggregations of other services and/orsoftware resources.

Still another object of the present invention is to provide acomposition utility which enables fast and efficient construction of webservices from other services and/or software resources.

A further object of the present invention is to leverage a dualaggregation model for web services.

Other objects and advantages of the present invention will be set forthin part in the description and in the drawings which follow and, inpart, will be obvious from the description or may be learned by practiceof the invention.

To achieve the foregoing objects, and in accordance with the purpose ofthe invention as broadly described herein, the present inventionprovides methods, systems, and computer program products for enablingprogrammatic management of software resources in a content frameworkenvironment.

In preferred embodiments, this technique comprises: defining a proxyingcomponent to act as an intermediary between the content aggregationframework and a software resource to thereby enable the contentaggregation framework to access and manage the software resource; anddefining, as the content aggregation framework functional interface ofthe proxying component, the operations which are available from thesoftware resource and defining, as the content aggregation frameworkmanagement interface of the proxying component, the managementoperations which are available from the software resource, therebyenabling access to, and management of, the software resource from thecontent aggregation framework using the content aggregation frameworkfunctional interface of the proxying component and the contentaggregation framework management interface of the proxying component forthe software resource.

Preferably, the software resource lacks a content aggregation frameworkfunctional interface that specifies operations which are available fromthe software resource and lacks a content aggregation frameworkmanagement interface that specifies management operations which areavailable from the software resource, and the proxying component isadapted for execution in the content aggregation framework by specifyinga content aggregation framework functional interface for the proxyingcomponent and a content aggregation framework management interface forthe proxying component.

The software resource may be a network-accessible service.

The technique may further comprise: invoking one or more operations ofthe content aggregation framework management interface of the proxyingcomponent, by the content aggregation framework at run time, to managethe software resource, wherein each of the invocations causes theproxying component to invoke a corresponding operation of the softwareresource.

The present invention will now be described with reference to thefollowing drawings, in which like reference numbers denote the sameelement throughout.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 provides a diagram illustrating the participants and fundamentaloperations of a service-oriented architecture, according to the priorart;

FIG. 2 illustrates a sample portal page in which content fromvisually-oriented portlets is rendered, according to the prior art;

FIG. 3 is a block diagram illustrating a portlet structured as a webservice proxy, according to preferred embodiments of the presentinvention;

FIGS. 4A and 4B illustrate the content of sample WSDL documentsspecifying a deployment interface and a system interface, respectively,according to preferred embodiments of the present invention;

FIG. 5 illustrates a graphical web service composition tool of the typewhich may be created according to the teachings of the presentinvention;

FIGS. 6, 7, 9, 12, 13, and 17 provide flowcharts depicting logic whichmay be used to implement preferred embodiments of the present invention;

FIG. 8 illustrates a web services stack which may be used in anetworking environment in which the present invention operates;

FIG. 10 provides a sample “tModel” which may be used to publishinformation to a registry;

FIGS. 11A-11C are used to illustrate signatures of methods, and the needto provide a signature superset when dynamic run-time binding is to beused;

FIG. 14 illustrates a sample “plug link” specification which isrepresentative of those used according to the present invention;

FIGS. 15A-15C provide syntax used to describe mapping of data betweenoperations;

FIG. 16 is a simple example of information that may be contained in atransformation registry; and

FIG. 18 provides an overview of components used in describing thepresent invention.

DESCRIPTION OF PREFERRED EMBODIMENTS

The promise of web services is that disparate applications will be ableto interoperate like never before, offering a new breed of seamlesshyper-integrated applications through openness and urbanization ofenterprise systems. Web services will make distributed softwareresources more widely available, and will allow software to be marketedas a service. As web services become widespread, there will be a needfor managing the services and for an aggregation point where theseservices can be aggregated to form new services which can then bedeployed. A content framework such as a portal platform provides manybuilt-in services for content management and service hosting, such aspersistence, personalization, and transcoding. The present inventiondefines novel techniques for leveraging portal platforms, extending theplatforms to provide for aggregation, deployment, and management of webservices. Providing access to software services through portalaggregation will lower integration costs and help speed time-to-market.This type of portal usage for application-to-application communicationmay be referred to as an “application portal”, in contrast to the“visual portals” which are designed to display information to humanusers. Companies providing application portals today promote low-costEnterprise Application Integration (“EAI”) and provide applicationaccess and management through a standard portal platform. However,existing EM products do not yet programmatically integrate web servicesnor do they integrate web services in real-time, and these existingproducts require that small “engagements” are manually provided as the“glue” necessary to define a static binding to hook web services into aportal before applications can be deployed. (For example, an engagementmay be needed to surface the interface to an enterprise's customerrelationship management, or “CRM”, software resources at the visualportal. The engagements often use proprietary software and/orcustom-defined XML communications. This approach is therefore notsuitable for dynamic, programmatic aggregation or integration on aglobal scale.) Current estimates are that creating such engagementsrequires anywhere from several days to several weeks. JamCracker, Onyx,and USInternetworking are among the companies providing EM usingapplication portals today. No systems are known to the inventors whichenable real-time deployment of software resources by aggregating them ina modeling composition tool, and then programmatically integrating andmanaging them using open industry standards as disclosed herein.

The present invention defines techniques for integrating web servicesand other back-end software resources into an application portalplatform using a portlet model or paradigm, thereby creating new webservices. One commercially-available portal platform on which thepresent invention may be implemented is the WebSphere® Portal Server(“WPS”) from the International Business Machines Corporation (“IBM”).(“WebSphere” is a registered trademark of IBM in the United States,other countries, or both.) Note, however, that while discussions hereinare in terms of a portal platform, the inventive concepts are applicableto other types of content frameworks which provide analogousfunctionality and are also applicable to portals other than WPS, andthus references to portals and their portlet paradigm is by way ofillustration and not of limitation. Using the disclosed techniques, anapplication portal functions not only as an access point for staticallyintegrating services after manually providing engagements, as in theprior art, but also functions as a full web service utility. In itscapacity as a web service utility, a portal platform according to thepresent invention provides programmatic management of web services anddynamic run-time integration of web services.

One aspect of the present invention also provides a tool for compositionor aggregation of new web services. Using this composition tool, asystems administrator (or, equivalently, a service composer or otherperson) may define a new service composed of more fine-grained services.According to preferred embodiments of this aspect, the fine-grainedservices from which other services are built may reside locally orremotely, and the techniques disclosed herein enable referencing thoseservices and using those services in a transparent manner without regardto whether they are local or remote. The fine-grained services mayinclude any form of programming logic, including script programs, Java™classes, COM classes, EJBs (“Enterprise JavaBeans”™), stored procedures,IMS or other database transactions, legacy applications, and so forth.(“Java” and “Enterprise JavaBeans” are trademarks of Sun Microsystems,Inc.) The web services created in this manner can then automatically bemanaged by the portal platform and can also be used in creating new webservices in a recursive manner, as will be described.

The disclosed techniques build on the portal concept of a plug-in, whichis referred to in the art as a “portlet”. Portlets are known in theprior art which are visual in nature. In the visual portal model, eachportlet is responsible for obtaining a portion of the content that is tobe rendered as part of the complete portal page for the user. Byconvention, the portlet's “service” method is invoked to return markuplanguage (such as Hypertext Markup Language, or “HTML”) syntaxencapsulating the result of the portlet's execution. Once the visualportlet's content has been aggregated with other markup language syntaxby the portal page from which it was invoked, the result is a Web pagewhose content is well suited for the needs of the portal page's humanuser. FIG. 2 provides an example of a prior art portal page 200 from avisual portal, where this portal page includes content from threevisually-oriented portlets (see elements 210, 220, 230). Portlet 210 inthis example displays news headlines. Portlet 220 shows a stock tickerfor the user's favorite stocks, and portlet 230 displays the currentweather and weather forecast for the user's selected city.

In many content-rich visual portals, the output of visually-orientedportlets is aggregated physically on the portal page according to theportlets' content categorization or taxonomy. For example, output ofnews feed portlets may be provided on one tabbed page of anotebook-style visual portal, with output of weather portlets on anothertabbed page and perhaps the output of portlets of interest to anenterprise's employees may be provided on another. Or, portlet outputmay be grouped within logical sections of a single portal page. Thephysical layout of the portal page may therefore enable end users tofind information more quickly and efficiently. Work is ongoing to buildremote interfaces to visually-oriented portlets such that visual portalscan aggregate content from applications which may be located on machinesother than the machine on which the portal code resides. This aggregatedcontent will then be presented on the portal page, and whether it wasobtained from a locally-available portlet or from a remote portlet willbe transparent to the end user. (See, for example, “WebSphere PortalServer and Web Services Whitepaper”, T. Schaeck, published by IBM on theInternet athttp://www-4.ibm.com/software/solutions/webservices/pdf/WPS.pdf, whichdiscusses remote interfaces to visually-oriented portlets.)

A portal platform provides a number of services for the portlets ithosts, as described above. The present invention leverages portlets as aportal interface, and also builds upon the concept of a remote portletinterface (where this concept is extended as disclosed herein to applyto programmatic portlets), to enable access to software resources.Portlets functioning according to the present invention are alsoreferred to herein as “web service intermediaries” or “web serviceproxies”, or simply as “intermediaries” or “proxies”. That is, a portletmay now act as an intermediary between an application or softwareresource requesting a particular service and a software resourceproviding that service. According to the present invention, the softwareresource performing a particular function may be statically bound to aweb service proxy (for example, at development time), or a web serviceproxy may be bound to a software resource which is dynamically selected(for example, based upon criteria which are evaluated at run-time). Ineither case, the portlet proxy receives request messages and forwardsthem to the software resource to which it is bound; once the softwareresource has completed the requested function, it returns its responseto the portlet proxy which then forwards the response to the requester.

A block diagram illustrating a portlet structured as a web service proxyis shown in FIG. 3. As shown therein, portlet proxy 340 includes adeployment interface 310, a system interface 320, and a functionalinterface 330. The portlet proxy communicates with a portal platform 300using these interfaces, acting as an intermediary between the portalplatform and the software resource 350 which carries out the function ofinterest. Details of each functional interface are specific to the webservice provided by software resource 350, and do not form part of thepresent invention. The present invention, however, makes the functionalinterface of the software resources available as an interface 330 of theportlet proxy. (Exposing the functional interface using WSDL definitionsand SOAP services may be accomplished using a commercially-availabletool such as the IBM Web Services Toolkit, or “WSTK”, during thedeployment process.) The deployment interface and system interface willbe described in more detail below.

The software resources invoked using the techniques of the presentinvention are typically designed for program-to-program interaction, butmay alternatively be visual in nature. For example, visually-orientedresources may be invoked during execution of a web service whichoperates primarily in a program-to-program manner. The term“programmatic portlet” is used herein to refer generally to portletproxies according to the present invention, whether or not theunderlying software resource involves visually-oriented code.

A deployment interface and a system interface are defined for eachportlet which serves as a web service proxy, according to preferredembodiments of the present invention. (In alternative embodiments,advantages of the present invention may be realized by implementingeither the deployment interface or the system interface separately, andsuch implementations are within the scope of the present invention. Forexample, there may be cases in which it may be desirable not toimplement management services for some web services. In such cases, thesystem interface may be omitted; alternatively, a system interface mightbe provided which has no operations or which has operations implementedas empty functions.) These new interfaces may also be referred to as thedeployment port type and system port type, respectively. A portletaccording to the present invention thus defines a service provider typethat includes the port types necessary for portal integration ofsoftware resources and service interaction and management. (“Port types”is a term used in the art to signify the specification of a portlet'soperations, and “service provider type” is a term used to signify acollection of port types.)

The deployment interface enables a portlet proxy (that is, an aggregatedweb service which is represented by a portlet proxy) to be used insubsequent web service composition operations, in a recursive manner.For example, the deployment interface of a portlet “A” providesinformation about portlet A for use as portlet A is aggregated withother portlets to form a new web service “Z”; by defining a deploymentinterface for web service Z, according to the present invention,information about web service Z can subsequently be provided as serviceZ is used for composing other new services.

The system interface is used for run-time management of portlets (thatis, of web services represented by portlet proxies) by the portalplatform. Use of the system interface allows the portal platform toperform functions such as logging of events, billing, and other types ofadministrative operations pertaining to execution of the web service.This requires 2-way communication between the portal platform and theportlet proxy, and uses novel techniques which are disclosed herein.

Referring now to the sample WSDL documents in FIGS. 4A and 4B(representing interface definitions), the deployment interfacespecification and system interface specification, respectively, areillustrated. According to preferred embodiments, the deployment andsystem port types are represented as WSDL documents for registration ina registry. As shown at 410 of the WSDL document 400 in FIG. 4A, theexample deployment interface is named “Deployment” and includesoperations such as “getDisplayName” and “getDisplayIcon16×16” (seeelement 430). These operations may be used, for example, to retrieve adescriptive name of the web service and to retrieve a graphic imagerepresenting the web service for placement on a palette of a web servicecomposition tool (such as that illustrated in FIG. 5). According to theWSDL specification, the input and output messages used for communicatingwith a service are specified in “<message>” elements 420, where theparameters used by those messages are defined as “<part>” elements.Thus, a message element is defined for each message of each operationspecified for this port type. (Refer to the WSDL specification for moreinformation about the details of a WSDL document.)

The WSDL document 450 in FIG. 4B defines the system interface, which inthe example is named “System” (see element 460). A complex data typenamed “Event” is defined (see element 470), comprising 2 stringparameters and a date parameter. This data type may be used, forexample, when exchanging logging data to be recorded in an auditing logfile. A “logEvent” operation is defined (see element 490), and in thisexample is a 1-way operation invoked using a “logEventReceive” message(see element 480) which has a parameter of type Event. In addition, theexample defines a “reportUsage” operation which has 2 messages“reportInput” and “reportOutput”.

The deployment port type is used at design time, and allows a new webservice to be composed with a web service composition tool such as thatillustrated by FIG. 5. The deployment port type contains operationspertinent to the modeling composition process. Representative examplesof operations which may be useful for this purpose include“getIcon16×16” and “getIcon32×32” to retrieve icons (such as 520 a, 520b) of different sizes for placement on a portlet palette (illustrated byelement 510), “getDisplayName” and “getDisplayDescription” to providetextual information for presenting to a service composer (such as thatillustrated at 521 a and 521 b), “getAuthorName” to retrieve anidentification of the software developer or the service composer, and soforth.

Turning now to FIG. 6, logic is depicted which may be used for creatinga portlet proxy for use in a composition tool such as that representedby the sample user interface of FIG. 5. Note that while the descriptionof FIG. 6 is presented herein in terms of preparing a WSDL documentdescribing the portlet's operations, this logic also outlines what isrequired for a developer creating source code for a software resource.For example, if the software resource will report information throughits system interface for quality of service or billing purposes, thedeveloper must provide code to gather the appropriate data and returnthis data when requested; the method or methods which perform thisfunction may then be identified as part of the system port type of theportlet proxy for the software resource. (See interface 320 of FIG. 3,for example, illustrating that the system interface of portlet proxy 340exposes the management operations of software resource 350.) Thisprocess comprises first determining the operations that will be exposedas the portlet proxy's published functional interface (Block 600). Forexample, suppose a programmatic portlet such as the portlet representedby icon 520 a in FIG. 5 provides order fulfillment services. The publicinterface of this portlet might include a method named“receivePurchaseOrder” (see element 530), which can be used to invokeoperations of the underlying software resource. Preferably, a humandetermines which methods of a software resource should be publiclyexposed; alternatively, programmatic operations could be used to selectthe methods which comprise the public interface. (For example,programmatic operations might be designed to select all public methodsfor exposing, or perhaps to select only the “getter” public methods.)

Once the public interface is identified, WSDL markup language syntax isprogrammatically created to specify this information. This comprisesgenerating <message> and <operation> elements, similar to thoseillustrated in FIGS. 4A and 4B. The composer may be asked to supplyinformation for use in this process, such as the port type name, thelocation of the name space information, and so forth. Or, thisinformation or parts thereof may be programmatically generated and/orretrieved from a configuration file.

Techniques for programmatic generation of markup language syntax (usinginput supplied by a human, as well as programmatically-derivedinformation) are known in the art, and a detailed description thereof isnot deemed necessary for an understanding of the present invention.IBM's WSTK is an example of a commercially-available product which maybe used to programmatically generate WSDL for an existing softwareresource. See “The Web services (r)evolution: Part 4, Web ServicesDescription Language (WSDL)”, G. Glass (Feb. 2001), published by IBM onthe Internet athttp://www-106.ibm.com/developerworks/webservices/library/ws-peer4,which presents an example of programmatically generating a WSDL documentfor a simple weather service which has “getTemp”and “setTemp”operations. FIG. 4 of this document illustrates asking a composer whichmethods of a class should be used in creating a public interface. Itshould be noted that references herein to using a WSDL syntax generatorare merely for purposes of illustration; alternatively, a developermight manually create WSDL documents or another type of markup languagesyntax tool might be used for this purpose.

In addition to specifying the public interface, the portlet's deploymentport type information must be created (Block 610). An example of thedeployment port type is illustrated in FIG. 4A. If the port typeinformation is programmatically generated, for example using WSTK, thisprocess comprises parsing the software resource's class definition tolocate its methods providing the operations of the predefined deploymentport type and to identify the parameters and parameter types of eachmethod, and then generating <message> and <operation> elements, as wellas <part> elements and <type> definitions as necessary. The composer maybe asked to provide input during this process, as needed, such aspopulating the parameters for the messages of the operations. (Forexample, to populate the “displayIcon16×16Output” parameter of the“getDisplayIcon16×16Output” message, the composer might specify theUniform Resource Locator, or “URL”, of a particular image file.) Theportlet's system port type information is also created (Block 620), in asimilar manner, resulting in a WSDL document such as that shown in FIG.4B. (In preferred embodiments, the deployment and system interfacedefinitions are placed in separate WSDL documents as shown in theexamples of FIGS. 4A and 4B because they describe different behavior.)

Finally, the portlet proxy for the web service is published to aregistry (Block 630), after which the portlet proxy is available for usein composing new web services and its services are available forinvocation (e.g. using a conventional UDDI find and bind). In preferredembodiments, documents known in the art as “tModels” are used forpublishing a portlet proxy's web services information to a registry. (A“tModel”, according to the UDDI specification, is metadata whichdescribes the specifications and the versions of specifications thatwere used to design published services. “tModel” is a generic term for aservice “blueprint”, defining the conventions to which the registeredservice conforms. For example, if a registered service includes an “HTTP1.1 tModel”, then this service is known to adhere to certainrequirements and conventions associated with that tModel—and, byimplication, adheres to particular requirements in its use of HTTP.)Note that a WSDL port type definition can be a tModel; it can also be apartial tModel, which is a tModel in a tModel set. Thus, a single tModelmay be used to register both the deployment and system interfaces.(Refer to the UDDI specification for more information on tModels andtModel sets.)

Referring now to FIG. 7, logic is shown which may be used to implement aservice modeling and deployment process via a web service compositiontool. Block 700 indicates that the new web service is modeled usingportlets as proxies or templates for the service being aggregated. Thatis, a portlet may serve as an intermediary for a web service or for alocal resource, defining an interface to the operations provided by oneor more back-end software resources. However, the actual softwareresource(s) providing that service on the back end might not be selectedand bound until run-time. The service composer is also able to reuse thecomposed templates and dynamically plug in different service providersfor a static (development-time) binding.

The web service composition tool preferably provides a portlet palettefor use in this modeling operation, where registered portlets for aparticular taxonomy or category are presented on the palette. Theservice composer then creates a new web service using the compositiontool, for example by right-clicking on a web service icon to display itsavailable methods and then using drag and drop operations to positionselected method invocations as operations for carrying out a service.FIG. 9, discussed below, illustrates logic with which information may begathered for use by the web service composition tool, including locatingthe appropriate web services to use when constructing the palette.

In preferred embodiments, a directed graph is used to model theoperations involved in executing the new web service. Selected portletoperations represent the nodes of the graph, and the graph edges whichlink the nodes represent potential transitions from one serviceoperation or process to another. These service links can be qualifiedwith one or more transition conditions, and also with data mappinginformation if applicable. The conditions specify under what conditionsthe next linked service should be invoked. Often, these conditions willbe determined using the results of a previous service invocation. Datamapping refers to the ability to link operations between portlet porttypes and transfer data from one operation to another. For example, thedata mapping information may indicate that the output parameters of oneservice are mapped to the input parameters of another service.

Preferred embodiments of the present invention leverage the Web ServicesFlow Language (“WSFL”) for directed graphs. In particular, WSFL'spersistent storage techniques and run-time evaluation techniques usingdirected graphs are added to a web services stack to operate upon thegraphs created by a service composer. For a detailed discussion of WSFL,refer to the WSFL specification, which is entitled “Web Services FlowLanguage (WSFL 1.0)”, Prof. Dr. F. Leymann (May 2001), available on theInternet from IBM athttp://www-4.ibm.com/software/solutions/webservices/pdf/WSFL.pdf, whichis hereby incorporated herein by reference as if set forth fully. (Notethat the WSFL specification discusses use of directed graphs formodeling web services, but does not teach directed graphs in combinationwith services which are provided by programmatic portlet proxies. TheWSFL specification defines a “plug link” mechanism, discussed in moredetail below with reference to Block 1380 of FIG. 13, which can be usedin a proxy model to map interfaces in a simple manner as describedherein. This plug link mechanism is used by preferred embodiments of thepresent invention as the persistent definition of integrating portletproxies to implement web services.)

A web services stack 800 used in preferred embodiments is illustrated inFIG. 8. Service flow support 810 is preferably provided by WSFL, asstated earlier. Service discovery 820 and service publication 830 arepreferably provided using UDDI. A WSDL layer 840 supports servicedescription documents. SOAP may be used to provide XML-based messaging850. Protocols such as HTTP, File Transfer Protocol (“FTP”), e-mail,message queuing (“MQ”), and so forth may be used for network support860. As discussed herein, WSDL is used to define web service port typesand to define how to invoke operations of these port types, and WSFL isused to aggregate the web services (and therefore to aggregate theirinterfaces). At run-time, services are found within a registry using theUDDI service discovery process, and bound to using information fromtheir WSDL definitions. The WSFL run-time then uses these (port type)definitions to aggregate the services. (Because the signatures of theoperations will typically not match one-to-one, the WSFL plug linkmechanism may be used to map between the operation interfaces.)

Referring again to the example composition tool user interface in FIG.5, the composer has selected to begin the new service with a “receivepurchase order” operation 530. For purposes of illustration, supposethis operation evaluates the items on an incoming purchase order todetermine whether they are in stock or not. Thus, a transition condition535 indicates that if an item is out of stock, the next service to beexecuted is “place order with supplier” 540, whereas if an item is instock, transition condition 545 applies and the next service to beexecuted for this item is “add item to invoice” 550. Upon occurrence ofsome event, such as receiving a shipment of new items or perhapsreceiving a notification that the item had to be ordered from thesupplier's supplier, transition condition 555 applies and a service“response from supplier” 560 is to be executed. Presumably, this serviceevaluates the supplier's response, and if a requested item wasdetermined to be available, transition condition 565 applies and theitem will be added to an invoice by service 550, whereas if a requesteditem is not available then transition condition 575 applies and the nextservice to be executed is “add item to backorder” 580. As will beobvious, the nodes and conditions illustrated in FIG. 5 are merely forpurposes of illustration. (Data mapping information has been omittedfrom the example.)

Turning now to FIG. 9, the process of obtaining information to presentto the service composer on the user interface of a composition toolduring execution of Block 700 of FIG. 7 preferably begins at Block 900by determining the taxonomy of interest. One way in which this may beperformed is to query the composer. As shown by the example in FIG. 5,the composer may have requested portlet proxies pertaining to itemordering services, and therefore palette 510 includes icons 520 a, 520 brepresenting an order fulfillment service and an order payment service.Once the taxonomy is known, the registry is programmatically scanned(Block 910) for portlets whose tModels indicate support for thattaxonomy. The scan also checks for tModels representing support for thedeployment interface disclosed herein, and optionally the systeminterface disclosed herein. See FIG. 10 for an example of a tModel thatmay be used to indicate support for the system service provider type ofthe present invention. (Optionally, a single tModel may be used torepresent both the deployment and system service provider types. Or, atModel similar to the one shown in FIG. 10 may be separately created forthe deployment service provider type.) Note that the WSDL document inFIG. 4B defines an interface template for portlet proxies conforming tothe sample tModel in FIG. 10. This correspondence is shown, for example,in the service provider type named in the descriptive information at1010, and in the file name wherein the service provider type forms partof the URL at 1020. The <overviewURL> element of a tModel functions as atype of import statement to reference a WSDL service specification, asis known in the art. This tModel, along with its associated key, ispublished as a technical blueprint for a portlet proxy registered in aUDDI registry.

Block 920 performs a test to see if any more portlets meeting thecurrent criteria are available in the registry. If not, then processingcontinues at Block 930 where the dynamically-gathered information isused in the modeling operation to assemble aggregated services asportlet proxies. Discussion of the modeling operation continues belowwith reference to Block 710 of FIG. 7.

When the test in Block 920 has a positive result, then the processing ofBlocks 940 through 980 is performed to obtain information about theregistered portlet proxy which has been located. Block 940 obtains theportlet proxy's deployment description, which is preferably implementedto provide a description of the web service, and Block 950 obtains itsdeployment author information. Use of this information was previouslydiscussed with reference to FIG. 5. For example, it may be used if thecomposer requests to see the properties of a web service presented onthe user interface of the composition tool.

Block 960 obtains information about the icon to be displayed for thisservice on the user interface of the composition tool. Preferably, thisinformation comprises an address such as a URL specifying where an iconimage is stored. Block 970 obtains the deployment operations for thisportlet, in effect determining what the portlet can do.

Preferably, obtaining the deployment information for the portlet proxyin Blocks 940 through 970 comprises executing well-known methods of thedeployment interface by issuing the corresponding message from theservice's deployment port type. For example, using the deployment porttype defined in FIG. 4A, the message “getDisplayIcon16×16Input” may beinvoked to obtain the portlet's 16 by 16 icon, and if the portlet has a“getDisplayIcon32×32Input” message, this message can be invoked toobtain the portlet's 32 by 32 icon. (Blocks 940 through 970 should beconsidered as representative of the information that may be beneficiallyretrieved for a portlet proxy; additional or different information maybe deemed useful in a particular implementation of the presentinvention.)

After obtaining the pertinent deployment information about the portlet,a representation of the portlet is added to the modeling palette (Block980), and control returns to Block 920 to determine if there are moreportlets of interest in the registry. The processing of Block 920 hasbeen described above.

Returning now to the discussion of FIG. 7, once the composer completesthe model of service interaction as a directed graph, at Block 710 thecomposer declares a service provider port type for the newly-aggregatedservice. In order to define this public interface, the composer mayselect operations to be exposed, or exported, within port types of theservice of the composition, thereby identifying the public port type.The composer may select as many operations for exporting as necessary,and may also define new operations if desired. (For example, thecomposer might decide to define a new name for an operation, and providea one-to-one mapping for that new name to the old name.) These exposedoperations specify the means for invoking the new service. For example,with reference to the sample directed graph in FIG. 5, the composerwould specify (at least) the operation “receivePurchaseOrder”corresponding to node 530 as a public interface. The composer may alsoprovide a data mapping between an exposed operation and an internalservice port type operation. For the sample directed graph in FIG. 5,having a public interface of “receivePurchaseOrder”, the composer mightspecify (for example) a data mapping that converts data to a particularformat required by this operation, such that an input parameter named“inputPurchaseOrder” adhering to a predefined type “purchaseOrder” wouldbe available to the service upon invocation. Providing the data mappingmay comprise identifying a canned transformation component, such as aninteger-to-float transform; identifying a stylesheet which contains anappropriate transformation, such as an XSLT (Extensible StylesheetLanguage Transformations) stylesheet; identifying customizedtransformation logic, which may for example convert one complex datatype to another; and so forth. (Refer to the discussion of FIGS.11A-11C, below, for more information about declaring the interface to aweb service intermediary and potential web service software resources,and about providing transformation information.) The process ofdeclaring the exposed port types (i.e. operations) results in the newservice provider type for the aggregated composition. Thus, this newcomposition is itself a portlet proxy, or web service intermediary, thatcan be used as a building block in further compositions.

The composer also provides a mapping for the deployment port type andfor the system port type, if applicable, such that the resulting webservice will be able to be used within a web service composition tooland will be able to be programmatically managed by the portal platformas disclosed herein. This is preferably accomplished by prompting thecomposer (using a menu-driven approach, for example) to identifyoperations and data mappings that will then be represented in WSFLmarkup language <export> and <dataLink> elements, which enable providinga new interface and doing internal mapping for that interface. (Refer tosection 4.5.3, “Data Links and Data Mapping”, and section 4.6.4,“Exporting Operations”, of the WSFL specification for more informationon the syntax and semantics of the <export> and <dataLink> elements.)

In some cases, it may be desirable to generate the deployment and/orsystem port types (and similarly, the public interface of the portletproxy) without reference to a particular target software resource. Forexample, suppose that run-time quality of service is an important factorin choosing a service provider for some service such as credit cardprocessing. To provide a more generic interface which willprogrammatically adapt to one of several target service providers aftera run-time service selection, according to the present invention, thecomposer may be asked to provide input for use in creating the WSDLdocument (see the description of Blocks 600 through 620); this processmay be assisted by parsing class definitions and having the composerpoint to the right operations. The examples in FIGS. 11A and 11B showsignatures that might exist for two candidate software resources for acredit card processing operation. The example in FIG. 11C shows a samplesignature that might be designed as a superset which includes allparameters for both possible candidates. The manner in which a run-timemapping of input parameter values to the parameters required by theselected resource occurs is described below.

In preferred embodiments, a WSFL “flow model” is used to persistentlystore the new service composition. Thus, the flow model of thenewly-composed web service is created (Block 720). This flow model istransmitted as a document accompanying the UDDI publish message for thenew web service (Block 730), after which the new web service becomesautomatically available to service requesters (such as other businessunits of an organization or its business partners). A WSFL flow model isa markup language specification of the execution sequence of thefunctionality provided by the web service which has been composed as adirected graph (where the directed graph was constructed duringexecution of Block 700). See section 8.4, “The Flow Models for Airlineand Agent”, in the WSFL specification for examples of flow models andtheir syntax. The WSFL specification provides a thorough description ofthe syntax requirements for flow models, and that discussion is notrepeated herein.

The flow model used with the present invention may be programmaticallyconstructed using the logic shown in FIG. 12, as will now be described.

The flow model construction process, wherein the directed graph createdby the composer is converted to a WSFL flow model, is shown in FIG. 12and begins at Block 1200 by locating the starting node of the graph. AWSFL activity element will be defined for each graph node, or operation,within the composition, as indicated by Block 1210, beginning from thelocated starting node. (Refer to the WSFL specification for a detaileddescription of the syntax of the elements created during the processingof FIG. 12.) Block 1220 then checks to see if this graph node has anyedges which have not yet been processed. If this test has a positiveresult, then processing continues at Block 1240 which defines a controllink for that edge. Control links will provide the flow betweenoperations, using the WSFL run-time, and thus represent the edges of thecomposition graph. These links are then weighted with the transitionconditions that specify the conditions under which that serviceinteraction will execute (Block 1250). Data links are added (Block 1260)to the control links, as appropriate, to define the mapping of databetween activity operations. Control then returns to Block 1220 to seeif this node has any more edges to be processed.

When the node's edges have all been processed, the test in Block 1220has a negative result and control transfers to Block 1230, which checksto see if any more nodes exist in the graph which have not yet beenprocessed. If this test has a positive result, control returns to Block1210 to begin processing the next graph node. Otherwise, the publicinterface to this service is defined (Block 1270) as a collection of thedeclared operations and port types specified as part of the serviceprovider type. Creation of the flow model document for this service isthen complete.

Note that while the WSFL run-time provides the means forprogrammatically constructing a flow model diagram from a directed graphwhich represents a web service, the present invention extends theexisting support by coupling this model with traditional portletaggregation (that is, aggregating predefined port types, as extendedherein to programmatic portlets) and injecting intelligent interfaceaggregation through external services. (This latter topic is describedin more detail below with reference to “convert-lets”.)

Returning to the discussion of FIG. 7, after publishing the flow modelto the registry, at Block 740 the service selection process is performedfor a newly-aggregated service. Service selection is the act of bindinga portlet (that is, the service provider type defined in the portletproxy's service definition) to an actual service provider (or providers)which provides software resources to fulfill that service process. Theservice selection operation may be performed according to the logicshown in FIG. 13, as will now be described.

Preferably, the composer uses a toolkit such as WSTK to access a UDDIregistry containing information about services that are available foraggregation. In Block 1300, an identification of the public or privateregistry to be queried is obtained. The composer may be prompted toenter this information; alternatively, it may be retrieved from a storedlocation such as a configuration file. The identification of one or moreservice taxonomies of interest is obtained (Block 1310), using similartechniques. The identified registry is then queried (Block 1320) forentries matching the selected taxonomy information. In Block 1330, thetModels of the located entries are checked to select only the registeredservices which are enabled for and which conform to the deployment (and,optionally, the system) port type(s) of the present invention.

Optionally, message mapping is performed in Block 1340 to map messagesand their associated data. The mapping provides one portion of the pluglink information; the other portion is the locator information discussedbelow (see Block 1350). Message mapping is typically required, and isoptional when there is a dual one-to-one correspondence betweenoperations. Mapping may be defined using several techniques, of the typewhich has been described earlier (such as using XSLT stylesheets,referencing program logic, and so forth). Or, “convert-lets” may be usedfor performing the mapping; convert-lets are described below withreference to FIG. 15C.

A service locator is defined (Block 1350), providing a mechanism tocontrol how the web service intermediary will bind to a web serviceimplementation. This may comprise creating a WSFL locator binding, usinga <locator> element to identify a WSDL or WSFL service definition; or,it may comprise creating a UDDI-type binding on a <locator> element.

A particular service provider can be selected by the composer as astatic binding, for example based upon information obtained from UDDIyellow pages descriptions, for a static development-time binding of theweb service intermediary to the service provider. Or, service providerselection can be specified as using a dynamic run-time binding, by usinga dynamic locator. Therefore, Block 1360 checks to see if the bindingwill be static or dynamic. If it is to be dynamic, the selection processwill be deferred until run-time, and the composer preferably indicatesone or more selection criteria (Block 1370) as UDDI service qualifiersto be used in the dynamic binding process. Examples of the semantics ofsuch criteria include: select a service provider using the first hitreturned from searching the registry; select a provider randomly; selecta service provider that matches specific service qualifiers; etc. Anexample was previously discussed in terms of matching quality of servicecriteria for selecting a credit card processing service provider. The<locator> element for a dynamic binding preferably contains query syntaxfor use with the UDDI find operation, specified as the value of the“selectionPolicy” attribute. (Refer to section 4.4.3, “ServiceLocators”, of the WSFL specification for more information on definingservice locator elements.)

At Block 1380, a plug link is generated for this web service. A WSFL“plug link” is a markup language specification of mappings between thesignature of the calling and called service provider operations (thatis, between the portlet proxy's standard interface and the interface ofthe web service implementation). Section 4.7, “Plug Links”, of the WSFLspecification describes plug links in more detail. FIG. 14 illustrates asample plug link 1400. In this example, the plug link specifies that ifthe “sendForm” message is received to invoke the “send” operation, it isto be mapped onto the “receiveForm” message to invoke the “receive”operation.

While plug links are known in the art, their use with portlet proxies isa novel aspect of the present invention. Note, however, that the datamapping support for plug links defined in the WSFL specificationprovides a relatively restricted form of data mapping. A <map> elementis provided, as shown at 1410, for a <dataLink> element of a flow model,which qualifies how to map one operation's message to another. The pluglink defined by WSFL is limited to specifying a source message, a singletarget message, a source message attribute, and a single target messageattribute. Thus, if one web service returned the markup document 1500shown in FIG. 15A, and needed to pass this information to an aggregatedweb service whose method signature was “submitName (Name: string)”, theexisting WSFL syntax allows specification of a mapping that would (forexample) pass the value of the <firstName> element from document 1500 asthe input parameter to the submitName method. An example <map> element1520 which may be used within a plug link document to provide thismapping is shown in FIG. 15B. This is somewhat limiting in thatoperation attributes might not always map one-to-one, andtransformations more complex than identifying an attribute for directtransfer might be necessary. For example, with reference to document1500, it might be desirable to concatenate the values of the <firstName>and <lastName> elements for transfer to the next operation.

The present invention, on the other hand, leverages the portal platformas an intelligent aggregator for programmatic portlets by extending the<map> element to include a specification of a <converter> attribute, asillustrated in FIG. 15C. (The <converter> attribute is referenced in theWSFL specification, section 4.5.3, “Data Links and Data Mapping”.However, no information is provided therein as to how this attribute isused or implemented. Instead, the WSFL specification merely mentionsthat a converter attribute can specify a user-provided function for datamapping and conversion, and then goes on to state that the attribute isnot yet supported.) As shown therein, the attribute value is specifiedas a Uniform Resource Name (“URN”) identifying the portal platform.Since the portlet proxies of the present invention represent a standardinterface for a web service aggregated in the portal platform (i.e. aweb service intermediary), the portal platform can be used as arepository of portlet-to-portlet operation transformations. Thesetransformations are referred to herein as “convert-lets”, and may bereferenced from the URN of a <converter>element. At run-time, the portalplatform will automatically select the appropriate convert-let from aportal transformation registry, such as the simplified transformationregistry 1600 depicted in FIG. 16, and apply the transformation betweenthe web service operations. The transformations specified in thisregistry (see element 1610) may be arbitrarily complex, and may beimplemented in a variety of ways. For example, an XSLT stylesheet mightbe specified, or a piece of code implemented as a JavaBean or perhapseven another portlet proxy (encapsulating a web service) could bespecified for performing a transformation. (As will be obvious to one ofskill in the art, the sample registry 1600 is merely one example of anapproach that may be used for identifying the convert-lets used forconverting data. For example, additional information might be containedin the registry, and formats other than the tabular format depicted inFIG. 16 might be used. In addition, the entries in this registry are notlimited to one-to-one mappings: alternatively, a collection or set of“From” portlets and/or “To” portlets might be specified. Furthermore,rules or other criteria for identifying a “From” or “To” portlet mightbe specified, rather than explicitly identifying the portlets by name.)

Optionally, if a transformation between two portlet proxy interfacesdoes not already exist when those portlet proxies are used in modeling anew web service, as may be determined by consulting a portal platform'stransformation registry, the service composer may be prompted to provide(or identify) an appropriate convert-let.

Note that while the processing of FIG. 13 has been described as anin-line part of creating a new web service (by virtue of the logic ofFIG. 7), this processing may also be performed for web services thathave already been created and stored in the registry, to enable thoseservices to be used according to the present invention by creating a webservice intermediary for the existing web service. In this case, thetModel validation of Block 1330 may be bypassed, as the deployment andsystem tModels will typically have not been created for the registeredweb service. The deployment port type is provided by mapping theappropriate operations of the web service, as described above withreference to FIG. 12. (The composer may specify new operations if theexisting web service does not provide the necessary operations. Forexample, if the web service does not include an operation to retrieveicons which will represent the service on the palette of the compositiontool, the composer may add these operations.) If the underlying softwareresources provide auditing information, the composer may specify amapping between these operations and the system port type. A WSFL pluglink is then generated to represent this mapping and data transfer, asdiscussed earlier.

Returning again to FIG. 7, once the service provider selection processof Block 740 is complete, a WSFL “global model” for the service bindingsis created (Block 750). A WSFL global model is a markup languagespecification of links between endpoints of web service interfaces, witheach link corresponding to one web service's interaction with anotherweb service's interface. WSFL plug links are used in the global model todescribe the interaction between the portlet proxy and the selectedservice provider (or, alternatively, a candidate service provider).Section 4.8, “Global Model”, of the WSFL specification describes globalmodels in more detail.

The global model (or models, if there is more than one candidate serviceprovider) are published to the registry (Block 760), in addition topublishing the flow model at Block 720, in order to specify bindinginformation for use with the newly-created service compositionrepresented by the flow model. Note that reuse of the flow model formore than one global model allows other service providers to beplug-linked into the service interaction flow through the portlet proxyby substituting a different global model. Additionally, publishing thecomposition's flow model in the registry allows for the flow model to beretrieved and decomposed so that elements can be added, removed, orchanged (e.g. in a web service composition tool such as that illustratedby FIG. 5) as necessary to create a new web service. (It may bedesirable in some cases to prevent this type of decomposition andmodification, for example when privacy or security is a concern. Forsuch cases, a capability for privately publishing the flow model may beprovided.)

Turning now to FIG. 17, the automated management of web services whichis facilitated by the system port type of the present invention will bedescribed in more detail. The system port type is used at run-time, andenables communication of life cycle events which are necessary for aportlet proxy to operate within a portal platform. These life cycleevents include operations such as “spawn” for creating a new instanceand “terminate” for terminating an instance. Additional life cycleevents include “call”, for executing an instance; “enquire”, forquerying the status of an instance; “suspend”, for suspending aninstance; and “resume”, for resuming an instance. The WSFL specificationdescribes these six life cycle events in more detail, and existing WSFLsupport is preferably used for implementing these six life cycle events.(The portal platform calls methods of visual portlets of the prior artfor carrying out such events, and the portal platform preferably calls aprogrammatic portlet according to the present invention in the samemanner.) The system port type also allows communication back to theportal platform for performing functions such as reporting of events fora log, reporting information for use in billing for services, reportingof quality of service data, reporting various types of run-timeexecution errors or other operational events, etc. These reporting-typefunctions may be referred to as an “auditing” interface of a portletproxy. In order for this auditing information to be sent to the portalplatform, the portlet proxy must have a way to initiate communicationswith the platform. This type of 2-way communication between a portalplatform and a portlet is not available in the prior art. According tothe present invention, this communication is made possible byregistering the portal platform itself as a web service which is thenaccessible from a registry. (This registration of the portal platformmay occur at any time before the platform begins interacting withprogrammatic portlets as disclosed herein, and thus this registrationhas been omitted from FIG. 17.)

When the portal platform deploys a portlet proxy which includes thesystem port type, the logic shown in FIG. 17 may be used to enablecommunication of data using the portlet proxy's auditing interface.Beginning in Block 1700, the portal platform searches the registry forthe portlet proxy it wants to communicate with. Preferably, this searchlooks for a web service having a tModel which specifies the systeminterface (and optionally the deployment interface) disclosed herein.Upon finding an appropriate web service, the portal platform binds tothe system port type of that web service (Block 1710). The portalplatform can now initiate communications with the portlet proxy. AtBlock 1720, the (previously-registered) portal platform programmaticallyprovides its URN to the portlet proxy (for example, by invoking a“setURN” method of the portlet proxy). The portlet proxy then uses thisURN to look up the portal platform's interface (from the portalplatform's information in the registry), as shown in Block 1730. Theportlet proxy then uses the portal platform's registered information tobind to its system port type (Block 1740). At this point, the 2-waycommunication is established and the portlet proxy can now initiatecommunications with the portal platform (by programmatically invokingthe appropriate operations of the platform). Block 1750 indicates thatthe portal platform may call life cycle operations of the portlet proxy,such as the “enquire” operation, and Block 1760 indicates that theportlet proxy may also call auditing operations of the portal platform,such as a “logEvent” or “reportUsage” operation which was previouslydescribed with reference to FIG. 4B.

FIG. 18 illustrates an overview of the components which have beendescribed herein. A portal platform 1800 includes (or accesses) atransformation registry 1805, which stores convertlets (i.e. mappingsbetween programmatic portlets). A first programmatic portlet 1820, whichincludes a deployment interface 1822, system interface 1824, and webservice functional interface 1826, needs to supply information to asecond programmatic portlet 1860 which includes similar interfaces 1862,1864, 1866. Presumably, portlet 1820 obtains this data from execution ofa first web service 1840, where plug link 1830 provides for programmaticinteractions between portlet 1820 and web service 1840, and portlet 1860will pass this data to a second web service 1880, using plug link 1870to programmatically interact with web service 1880. A transformation isrequired in this example before the data can be passed between theprogrammatic portlets. This transformation will be performed byconvert-let 1850, which has been programmatically retrieved from thetransformation registry 1805, as shown at 1852. The WSFL run-time 1810coordinates and manages these interactions through execution of the flowmodels and global models which have been created to represent theprogrammatic portlets 1820, 1860 and their interfaces to the web serviceimplementations 1840, 1880, rendering the WSFL markup by flowing thedefined work flow and calling the appropriate activities through thedefined mappings (or the dynamically-determined mappings specified byconvert-lets).

As has been demonstrated, the present invention provides advantageoustechniques for aggregating, deploying, and managing web services. A dualaggregation model was disclosed, whereby a WSFL run-time provided formodeling aggregation of services was combined with traditional portalaggregation services available through a portal platform (and extendedas disclosed herein to address programmatic portlets), thereby providingthe “glue” for using programmatic portlets in a portal platform toenable aggregating programmatic portlets in a portal in real-time. Thedisclosed techniques enable this to occur programmatically, withoutrequiring manual intervention. Programmatic portlets are modeled as webservice intermediaries to either local software resources or remoteresources, and/or other portlets. Web service models are expressed andpublished as WSFL flow models, and service providers are linked usingWSFL global model expressions. Open standards are leveraged for businessprocess modeling and integration, defining significant advances in theweb services field. Note that while particular standards (such as WSFL)have been referenced when describing preferred embodiments, this is forpurposes of illustrating the inventive concepts of the presentinvention. Alternative means for providing the analogous functionalitymay be used without deviating from the scope of the present invention.

As will be appreciated by one of skill in the art, embodiments of thepresent invention may be provided as methods, systems, or computerprogram products. Accordingly, the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment, oran embodiment combining software and hardware aspects. Furthermore, thepresent invention may take the form of a computer program product whichis embodied on one or more computer-usable storage media (including, butnot limited to, disk storage, CD-ROM, optical storage, and so forth)having computer-usable program code embodied therein.

The present invention has been described with reference to flow diagramsand/or block diagrams of methods, apparatus (systems), and computerprogram products according to embodiments of the invention. It will beunderstood that each flow and/or block of the flow diagrams and/or blockdiagrams, and combinations of flows and/or blocks in the flow diagramsand/or block diagrams, can be implemented by computer programinstructions. These computer program instructions may be provided to aprocessor of a general purpose computer, special purpose computer,embedded processor or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions specified in theflow diagram flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function specified in the flow diagram flow or flowsand/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflow diagram flow or flows and/or block diagram block or blocks.

While the preferred embodiments of the present invention have beendescribed, additional variations and modifications in those embodimentsmay occur to those skilled in the art once they learn of the basicinventive concepts. Therefore, it is intended that the appended claimsshall be construed to include the preferred embodiments and all suchvariations and modifications as fall within the spirit and scope of theinvention.

1. A computer-implemented method of enabling programmatic management ofsoftware resources in a content aggregation framework, comprising:defining a proxying component to act as an intermediary between thecontent aggregation framework and a software resource to thereby enablethe content aggregation framework to access and manage the softwareresource, wherein: the software resource lacks a content aggregationframework functional interface that specifies operations which areavailable from the software resource and lacks a content aggregationframework management interface that specifies management operationswhich are available from the software resource; and the proxyingcomponent is adapted for execution in the content aggregation frameworkby specifying a content aggregation framework functional interface forthe proxying component and a content aggregation framework managementinterface for the proxying component; and defining, as the contentaggregation framework functional interface of the proxying component,the operations which are available from the software resource anddefining, as the content aggregation framework management interface ofthe proxying component, the management operations which are availablefrom the software resource, thereby enabling access to, and managementof, the software resource from the content aggregation framework usingthe content aggregation framework functional interface of the proxyingcomponent and the content aggregation framework management interface ofthe proxying component for the software resource.
 2. The methodaccording to claim 1, wherein the software resource is anetwork-accessible service.
 3. The method according to claim 1, furthercomprising invoking one or more operations of the content aggregationframework management interface of the proxying component, by the contentaggregation framework at run time, to manage the software resource,wherein each of the invocations causes the proxying component to invokea corresponding operation of the software resource.
 4. A system forenabling programmatic management of software resources in a contentaggregation framework, comprising: a computer comprising a processor;and instructions which are executable, using the processor, to implementfunctions comprising: defining a proxying component to act as anintermediary between the content aggregation framework and a softwareresource to thereby enable the content aggregation framework to accessand manage the software resource, wherein: the software resource lacks acontent aggregation framework functional interface that specifiesoperations which are available from the software resource and lacks acontent aggregation framework management interface that specifiesmanagement operations which are available from the software resource;and the proxying component is adapted for execution in the contentaggregation framework by specifying a content aggregation frameworkfunctional interface for the proxying component and a contentaggregation framework management interface for the proxying component;and defining, as the content aggregation framework functional interfaceof the proxying component, the operations which are available from thesoftware resource and defining, as the content aggregation frameworkmanagement interface of the proxying component, the managementoperations which are available from the software resource, therebyenabling access to, and management of, the software resource from thecontent aggregation framework using the content aggregation frameworkfunctional interface of the proxying component and the contentaggregation framework management interface of the proxying component forthe software resource.
 5. The system according to claim 4, wherein thesoftware resource is a network-accessible service.
 6. The systemaccording to claim 4, wherein the functions further comprise invokingone or more operations of the content aggregation framework managementinterface of the proxying component, by the content aggregationframework at run time, to manage the software resource, wherein each ofthe invocations causes the proxying component to invoke a correspondingoperation of the software resource.
 7. A computer program product forenabling programmatic management of software resources in a contentaggregation framework, the computer program product embodied on one ormore non-transitory computer-readable storage media and comprisingcomputer-readable program code for: defining a proxying component to actas an intermediary between the content aggregation framework and asoftware resource to thereby enable the content aggregation framework toaccess and manage the software resource, wherein: the software resourcelacks a content aggregation framework functional interface thatspecifies operations which are available from the software resource andlacks a content aggregation framework management interface thatspecifies management operations which are available from the softwareresource; and the proxying component is adapted for execution in thecontent aggregation framework by specifying a content aggregationframework functional interface for the proxying component and a contentaggregation framework management interface for the proxying component;and defining, as the content aggregation framework functional interfaceof the proxying component, the operations which are available from thesoftware resource and defining, as the content aggregation frameworkmanagement interface of the proxying component, the managementoperations which are available from the software resource, therebyenabling access to, and management of, the software resource from thecontent aggregation framework using the content aggregation frameworkfunctional interface of the proxying component and the contentaggregation framework management interface of the proxying component forthe software resource.
 8. The method according to claim 7, wherein thesoftware resource is a network-accessible service.
 9. The methodaccording to claim 7, further comprising invoking one or more operationsof the content aggregation framework management interface of theproxying component, by the content aggregation framework at run time, tomanage the software resource, wherein each of the invocations causes theproxying component to invoke a corresponding operation of the softwareresource.